Rsp platform selection for providing esim profiles to user devices

ABSTRACT

Telecommunication services are received at a user device using an embedded subscriber identity module (eSIM) profile stored on the user device while the user device is located in a first geographical area. A list of preferred remote SIM provisioning (RSP) platforms that provide eSIM profiles specific to a partner MNO of the MNO in a second geographical area is also received from an eSIM management platform of an MNO; The user device is then determined to have moved to a second geographical area based on a geolocation of the user device. Subsequently, an additional eSIM profile specific to the partner MNO of the MNO is downloaded to the user device from an RSP platform of one or more RSP platforms included in the list of preferred RSP platforms.

CROSS REFERENCE TO RELATED PATENT APPLICATION

This patent application is a divisional application of U.S. patentapplication Ser. No. 16/571,020, filed on Sep. 13, 2019, entitled “RSPPlatform Selection for eSIM Profile Procurement,” which is herebyincorporated by reference in its entirety.

BACKGROUND

The use of Embedded Universal Integrated Circuit Cards (eUICCs), alsoreferred to as Embedded Subscriber Identity Modules (eSIMs), is becomingincreasingly prevalent in consumer and machine-to-machine (M2M)communication fields. Unlike a traditional UICC or SIM card that existsas a removable smart card that is transferrable between multipledevices, an eUICC is an integrated circuit that is not designed to beuser removable, i.e., it is generally embedded with or soldered to otherelectronic components of a device.

An eUICC may be provisioned with one or more eSIM profiles, in whicheach eSIM profile contains a unique international mobile subscriberidentity (IMSI) number that authenticates a subscriber to a mobilenetwork operator (MNO). Other data that are stored in the eSIM profilemay include carrier network information, security authenticationinformation, a list of accessible network services, and/or so forth. TheMNO may transfer an eSIM profile to the eUICC of a user device via anover-the-air (OTA) update. For example, the user device may be aconsumer. Consumer devices are network-capable devices that aregenerally marketed to individual consumers. For example, these devicesmay include a smartphone, a tablet computer, a smartwatch, a gamingconsole, and/or so forth.

MNOs generally use Remote SIM provisioning (RSP) platforms that areoperated by third parties to provision the eSIM profiles to the eUICCsof user devices. In many instances, an RSP platform may be provided byan eSIM profile vendor that operates a GSM Association (GSMA)-certifieddata center. For example, the eSIM profile vendor may be an eUICCmanufacturer (EUM), and thus is able to generate eSIM profiles forinstallation in the eUICCs.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures, in which the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 illustrates an example architecture that enables a Local ProfileAssistant (LPA) application on a user device to selectively download anew eSIM profile from a particular RSP platform based on a RSP platformlist provided by an eSIM management platform.

FIG. 2 is a block diagram showing various components of one or moreillustrative computing devices that support the eSIM management platformfor generating and distributing RSP platform lists.

FIG. 3 is a block diagram showing various components of an illustrativeuser device that executes the LPA application to selectively download anew eSIM profile.

FIG. 4 is a flow diagram of an example process for an LPA application ona user device to obtain a new eSIM profile from an RSP platform that islisted on a preferred RSP platform list provided by the eSIM managementplatform.

FIG. 5 is a flow diagram of an example process for an eSIM managementplatform to send an RSP platform list of available RSP platforms to anLPA application on a user device.

FIG. 6 is a flow diagram of an example process for an eSIM managementplatform to determine whether an RSP platform is to be included in anRSP platform list.

DETAILED DESCRIPTION

This disclosure is directed to techniques that enable a Local ProfileAssistant (LPA) application on a user device to download a new eSIMprofile from a particular RSP platform when the user device moves from acurrent geographical area into a new geographical area. The user devicemay be a subscriber device of an MNO that is using a current eSIMprofile stored in the eSIM of the user device to receivetelecommunication services from a wireless carrier network of the MNOwhile in the current geographical area. Following the download of thenew eSIM profile from the particular RSP platform to the eSIM of theuser device by the LPA application, the LPA application may deactivatethe current eSIM profile stored in the eSIM of the user device andactivate the new eSIM profile once the user device moves into a newgeographical area. The new eSIM profile as activated may enable the userdevice to obtain telecommunication services from a wireless carriernetwork operated by a partner MNO of the MNO while in the newgeographical area. In this way, the user device may use the wirelesscarrier network of the partner MNO without having to roam on thewireless carrier network of the partner MNO. The lack of roaming mayresult in the elimination of roaming charge and/or implementation ofdiscounted billing to a subscriber account of a subscriber that ispaying for the telecommunication service usage of the user device.

In various embodiments, an eSIM management platform of the MNO mayprovide multiple lists of RSP platforms that correspond to differentgeographical areas for download to the user device. The eSIM managementplatform may provide new lists of RSP platforms as well as updated listsof RSP platforms. In some embodiments, the eSIM management platform maydistribute the multiple lists of RSP platforms via a push-model in whichthe eSIM management platform automatically sends the lists of RSPplatforms to the LPA application of the user device on a periodic basisor on the occurrence of certain events (e.g., user device registeringwith the wireless carrier network of the MNO, user device approachingwithin a predefined distance of a geographical area boundary). In otherembodiments, the eSIM management platform may distribute the multiplelists of RSP platforms via a pull-model, in which the LPA application ofthe user device may request the lists of RSP platforms on a periodicbasis or on the occurrence of certain events (e.g., user device poweringon, rebooting, etc.).

Each list for a particular geographical area may include one or multipleRSP platforms that have been selected by the MNO to provide an eSIMprofile of a partner MNO of the MNO. In instances in which a listcontains multiple RSP platforms, the multiple RSP platforms may belisted in the list according to an order of preference. In this way, theLPA application of the user device may obtain an eSIM profile of apartner MNO from a most preferred RSP platform. However, in the eventthe LPA application is unable to obtain the eSIM profile from the firstRSP platform, the LPA application of the user device may attempt toobtain the eSIM profile from a next most preferred RSP platform in thelist. Accordingly, the LPA application may proceed down the list in theevent of one or more additional eSIM profile download failures until theLPA application is able to obtain the eSIM profile from an RSP platformon the list.

In some embodiments, the eSIM management platform of the MNO may analyzethe service features of various candidate RSP platforms to determinewhether each RSP platform is to be included in a list of RSP platforms.The service features of an RSP platform may include a geographical areaserviced by the RSP platform, an availability of the RSP platform todistribute eSIM profiles, a representative (e.g., average) response timeof the RSP platform to requests for eSIM profiles, a reliability of theRSP platform in distributing eSIM profiles, available inventoryquantities of eSIM profiles for different user device types that arecarried by the RSP platform, and/or so forth. In this way, the MNO maymaintain control not only over the selection of specific RSP platformsthat are to supply eSIM profiles, but also the quality of serviceprovided by the RSP platforms.

The distribution of lists of available RSP platforms for differentgeographical areas to a user device enables the LPA application on theuser device to directly request an eSIM profile from an RSP platform asthe user device travels to a new geographical area. The use of an eSIMprofile for a partner MNO in the new geographical area may allow theuser device to avoid accruing out-of-network roaming fees for using thetelecommunication services provided by the partner MNO. In someinstances, the use of such an eSIM profile by the user device may alsoenable the user device to receive higher quality services and/oradditional service features from the partner MNO. The techniquesdescribed herein may be implemented in a number of ways. Exampleimplementations are provided below with reference to the following FIGS.1-6.

Example Architecture

FIG. 1 illustrates an example architecture 100 that enables a LocalProfile Assistant (LPA) application on a user device to selectivelydownload a new eSIM profile from a particular RSP platform based on anRSP platform list provided by an eSIM management platform. the userdevice 102 may be a consumer device. Consumer devices arenetwork-capable devices that are generally marketed to individualconsumers. For example, these devices may include a smartphone, a tabletcomputer, a smartwatch, a gaming console, and/or so forth. The userdevice 102 may be capable of obtaining telecommunication and/or datacommunication services from the mobile network operator (MNO) 104. TheMNO 104 may provide a wide range of mobile communication services, aswell as ancillary services and features, to subscribers and associatedmobile device users. In various embodiments, the MNO 104 may operate awireless carrier network that serves multiple user devices. The wirelesscarrier network may also relay communications between the multiple userdevices and user devices that are serviced by other telecommunicationsnetworks. The telecommunication services provided may include voicecommunication, multimedia communication, data communication, such asemail, messaging, content streaming, content uploading, and/or so forth.

The wireless carrier network of the MNO 104 may be implemented usingmultiple interconnected networks. In various embodiments, the wirelesscarrier network may include multiple Radio Access Networks (RANs). TheRANs may be connected to each other via regional ground networks. Inturn, the regional ground networks may be connected to a core network bya wide area network (WAN). Each regional portion of the MNO 104 mayinclude one or more RANs and a regional circuit and/or packet-switchednetwork and associated signaling network facilities. The MNO 104 mayprovide telecommunication services in accordance with one or moretechnical standards, such as Enhanced Data Rates for GSM Evolution(EDGE), Wideband Code Division Multiple Access (W-CDMA), High SpeedPacket Access (HSPA), Long Term Evolution (LTE), CDMA-2000 (CodeDivision Multiple Access 2000), 5th Generation (5G), and/or so forth. Insome embodiments, the core network of the MNO 104 may be accessed viawired or wireless local area networks (LANs). For example, a wirelesslocal area network may be a network that is established using Wi-Fi orBluetooth standards and hardware. In various embodiments, the MNO 104provides a home wireless carrier network to the user device 102. Forexample, the user device 102 may be registered with the MNO 104, and thewireless carrier network of the MNO 104 is the default provider oftelecommunication services to the user device 102.

However, the user device 102 may from time to time obtaintelecommunication service from other wireless carrier networks that arepartner MNOs of the MNO 104, such as a partner MNO 106. The partner MNOsgenerally operate wireless carrier networks in geographical areas thatare not served by the MNO 104. For example, the wireless carrier networkprovided by the MNO 104 may lack telecommunication network coverage in aparticular geographical area. As a result, the MNO 104 may have one ormore partner MNOs that do provide telecommunication network coverage inthe particular geographical area. For example, the MNO 104 may operate aU.S. wireless carrier network, and a partner MNO of the MNO 104 mayoperate a European wireless carrier network. Nevertheless, in someinstances, the MNO 104 and the partner MNOs may operate wireless carriernetworks that have overlapping telecommunication network coverage.

The user device 102 may use an eSIM profile 108 that is stored in anembedded Subscriber Identity Module (eSIM) 110 of the user device 102 toauthenticate to the MNO 104 in order to obtain telecommunicationservices from the MNO 104. For example, the eSIM profile 108 may containa unique international mobile subscriber identity (IMSI) number thatauthenticates the user device 102 to the MNO 104. Other data that arestored in the eSIM profile may include carrier network information,security authentication information, a list of accessible networkservices, and/or so forth, that are specific to the MNO 104. An eSIMprofile that enables a user device to access a wireless carrier networkof a particular MNO as a home wireless carrier network is referred to asan MNO-specific eSIM profile of that particular MNO. Accordingly, theeSIM profile 108 is an MNO-specific eSIM profile of the MNO 104.Nevertheless, in most instances, the eSIM profile 108 is also configuredto enable the user device 102 to roam on the wireless carrier networksof the partner MNOs.

In some embodiments, a local profile assistant (LPA) application 112 onthe user device 102 may be configured to download a particular eSIMprofile associated with a partner MNO, such as the partner MNO 106. Insuch embodiments, the download of the eSIM profile may occur when theuser device 102 moves to a geographical area that is served by thewireless carrier network of the partner MNO and unserved by the wirelesscarrier network of the MNO 104. Accordingly, the particular eSIM profilemay enable the user device 102 to obtain optimal network performancefrom the wireless carrier network provided by the partner MNO. In someinstances, the use of the particular eSIM profile by the user device 102may also enable a subscriber associated with the user device 102 to paya discounted rate for the telecommunication services provided by thepartner MNO. For example, the discounted rate may be less than a roamingrate that would be otherwise paid by the subscriber for having the userdevice 102 roam on the wireless carrier network of the partner MNO viathe eSIM profile 108.

The user device 102 may download eSIM profiles associated with variousMNOs from multiple RSP platforms. For example, an RSP platform may sendone or more data packets that contain an eSIM profile to a modem of theuser device 102 via an over-the-air (OTA) update. The data packets areassembled by the software of the modem into the eSIM profile and loadedinto the eSIM 110 of the user device 102. In various embodiments, eachof the multiple RSP platforms may be responsible for the management ofeSIM profiles that are specific to one or more MNOs. Accordingly, eachof the RSP platforms may include one or more subscription managers thatare executed by one or more computing devices. In some embodiments, eachof the RSP platforms may include at least one Subscription Manager DataPreparation (SM-DP), at least one Subscription Manager Data PreparationPlus (SM-DP+), and at least one Subscription Manager Secure Routing(SM-SR).

In various embodiments, the eSIM profiles for user devices, such as theuser device 102, may be initially loaded into profile state stores of anSM-DP+ operated by an RSP platform. In some instances, each profile datastore of the SM-DP+ may hold consumer eSIM profiles of a single MNO. Inother instance, a single profile data store of an SM-DP+ may hold eSIMprofiles of multiple different MNOs. Accordingly, each SM-DP+ isresponsible for managing the eSIM profiles of a different MNO, ormultiple SM-DP+s can collectively manage eSIM profiles of a single MNO.Thus, the SM-DP+s may distribute eSIM profiles to the user devices inresponse to requests from the user devices.

The backend servers of the MNO 104 may provide an eSIM managementplatform 114. The eSIM management platform 114 may serve as an interfacebetween an operational function of the MNO 104 (e.g., operation supportsystem (OSS), business support system (BSS), and/or so forth), multipleRSP platforms, and/or user devices. Accordingly, the eSIM managementplatform 114 enables the MNO 104 to manage eSIM profiles for deploymentinto eSIMs of user devices.

In various embodiments, the eSIM management platform 114 of the MNO 104may provide multiple lists of RSP platforms, such as the preferred RSPplatform lists 116(1)-116(K), which correspond to different geographicalareas to the user device 102. Each of the lists may identify one or morepreferred RSP platforms that are selected by the MNO 104 to distributeeSIM profiles in a corresponding geographical area. The one or more RSPplatforms in a list for a geographical area may be authorized todistribute eSIM profiles that are specific to a particular MNO. An eSIMprofile is specific to a particular MNO when the eSIM profile designatesa wireless network of the particular MNO as a home wireless carriernetwork. For example, the list 116(1) may identify the RSP platforms118(1)-118(M) as selected by the MNO 104 to distribute eSIM profiles ina specific geographical area. In some instances, the eSIM profilesdistributed by the RSP platforms 118(1)-118(M) may be specific to theMNO 104. In other instances, the eSIM profiles distributed by the RSPplatforms 118(1)-118(M) may be specific to a partner MNO of the MNO 104,such as the partner MNO 106. The eSIM management platform 114 may sendone or more of lists of the RSP platforms as a preferred RSP platformfile, such as the preferred RSP platform file 120, to the user device102. Each list of the RSP platforms may be a new list or an update to anexisting list already stored in the user device 102. Each list of RSPplatforms for a corresponding geographical area may be organized in anorder of preference, e.g., from a most preferred RSP platform to a leastpreferred RSP platform. For example, the preferred RSP platform list116(1) may indicate that the RSP platform 118(1) is the most preferred,the RSP platform 118(2) is the next most preferred, and the RSP platform118(M) is the least preferred.

The eSIM management platform 114 of the MNO 104 may analyze servicefeatures of various candidate RSP platforms to determine whether each ofthe various candidate RSP platforms is to be included in a list of RSPplatforms. The service features of an RSP platform may include ageographical area serviced by the RSP platform, an availability of theRSP platform to distribute eSIM profiles, a representative (e.g.,average) response time of the RSP platform to requests for eSIMprofiles, a reliability of the RSP platform in distributing eSIMprofiles, available inventory quantities of eSIM profiles for differentuser device types that are carried by the RSP platform, and/or so forth.

In various embodiments, an eSIM management platform 114 may distributethe preferred RSP platform file 120 to the user device 102 via apull-model or a push-model. In the pull-model, the LPA application 112is configured to request an updated version of the preferred RSPplatform file 120 from the eSIM management platform 114 for storage inthe eSIM 110 on a periodic basis or on the occurrence of certain events(e.g., user device powering on, rebooting, etc.). In the push-model, theeSIM management platform 114 may send the most updated version of thepreferred RSP platform file 120 to the LPA application 112 periodicallyor on the occurrence of certain events (e.g., user device registeringwith the wireless carrier network of the MNO, user device approachingwithin a predefined distance of a geographical area boundary). In turn,the LPA application 112 may store the most updated version in the eSIM110. Each list of preferred RSP platforms for a correspondinggeographical area may be organized in an order of preference, e.g., froma most preferred RSP platform to a least preferred RSP platform.

In operation, the user device 102 may initially access telecommunicationservices from the MNO 104 using the eSIM profile 108 that is specific tothe MNO 104 while the user device 102 is located in a first geographicalarea. Subsequently, the LPA application 112 may detect that the userdevice 102 has moved to a second geographical area. The secondgeographical area may be an area that is not covered by the wirelesscarrier network of the MNO 104, but which is covered by the wirelesscarrier network of the partner MNO 106.

Following such detection, the LPA application 112 may retrieve aparticular list of preferred RSP platforms that corresponds to thesecond geographical area from the preferred RSP platform file 120 storedin the eSIM 110. Subsequently, the LPA application 112 may download aneSIM profile from the most preferred RSP platform on the particularlist. For example, if the RSP platform 118(1) is the most preferred RSPplatform, the LPA application 112 may send an eSIM profile request 126to the RSP platform 118(1). In response, the RSP platform 118(1) maysend an eSIM profile 128 that is specific for the partner MNO 106 to theuser device 102 for storage in the eSIM 110. The eSIM profile 128 isthen used by the user device 102 to access telecommunication servicesfrom the partner MNO 106 while the user device 102 is in the secondgeographical area.

However, in the event the LPA application 112 is unable to obtain theeSIM profile from the first RSP platform, the LPA application 112 mayattempt to obtain the eSIM profile from a next most preferred RSPplatform on the particular list. Accordingly, the LPA application 112may proceed down the list in the event of one or more additionalfailures until the LPA application 112 is able to obtain the eSIMprofile from an RSP platform on the list.

Example eSIM Management Platform

FIG. 2 is a block diagram showing various components of one or moreillustrative computing devices that support the eSIM management platformfor generating and distributing RSP platform lists. The computingdevices 200 may include a communication interface 202, one or moreprocessors 204, memory 206, and hardware 208. The communicationinterface 202 may include wireless and/or wired communication componentsthat enable the computing devices 200 to transmit data to and receivedata from other networked devices. The hardware 208 may includeadditional user interface, data communication, or data storage hardware.For example, the user interfaces may include a data output device (e.g.,visual display, audio speakers), and one or more data input devices. Thedata input devices may include, but are not limited to, combinations ofone or more of keypads, keyboards, mouse devices, touch screens thataccept gestures, microphones, voice or speech recognition devices, andany other suitable devices.

The memory 206 may be implemented using computer-readable media, such ascomputer storage media. Computer-readable media includes, at least, twotypes of computer-readable media, namely computer storage media andcommunications media. Computer storage media includes volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules, orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD), high-definition multimedia/data storage disks, orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other non-transmissionmedium that can be used to store information for access by a computingdevice. In contrast, communication media may embody computer-readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave, or other transmissionmechanisms. In other embodiments, the computing devices 200 orcomponents thereof may be virtual computing devices in the form ofvirtual machines or software containers that are hosted in a computingcloud.

The computing devices 200 may implement the eSIM management platform114. The implementation involves the execution of software,applications, and/or modules that include routines, programinstructions, code segments, objects, and/or data structures thatperform particular tasks or implement particular abstract data types.The eSIM management platform may include an interface module 210, acollection module 212, and a distribution module 216. The interfacemodule 210 may enable the eSIM management platform 114 to communicatewith the operational function of the MNO 104. The interface module 210may further enable the eSIM management platform 114 to communicate withfunctions of RSP platforms and LPA applications via a standard protocol,such as the hypertext markup language protocol (HTTP). In someinstances, the interface module 210 may call one or more APIs of theoperational function or the RSP platform to perform operations.Alternatively, or concurrently, the interface module 210 may include oneor more APIs that are callable by the operational function, the RSPplatforms, and the LPA applications to perform operations. Suchoperations may include receiving service feature data from RSP platformsand distributing the preferred RSP platform files to the LPAapplications on user devices.

In some embodiments, the interface module 210 may include anauthentication function that controls access by the RSP platforms andthe LPA applications. For example, an interface function of each RSPplatform may submit a corresponding authentication credential to theinterface module 210 when the RSP platform initially registers with theeSIM management platform 114. For example, the authentication credentialmay include an RSP identifier and a unique authentication token. Theauthentication credential of each RSP platform is stored by the eSIMmanagement platform 114 in an authentication credential data store 220.Accordingly, the interface function of an RSP platform may submit anauthentication credential in order to interface with the eSIM managementplatform 114. In turn, the eSIM management platform 114 may validate thesubmitted authentication credential against the stored authenticationcredential for the RSP platform to determine whether the RSP platform isto be granted interface access.

Likewise, an LPA application may submit a corresponding authenticationcredential to the interface module 210 when the LPA applicationinitially registers with the eSIM management platform 114. For example,the authentication credential may include an application identifier anda unique authentication token. The authentication credential of each LPAapplication is stored by the eSIM management platform 114 in theauthentication credential data store 220. Accordingly, the interfacefunction of the LPA application may submit an authentication credentialin order to interface with the eSIM management platform 114. In turn,the eSIM management platform 114 may validate the submittedauthentication credential against the stored authentication credentialfor the LPA application to determine whether the LPA application is tobe granted interface access. In various embodiments, the computingdevices of the eSIM management platform 114, the LPA applications, andthe RSP platforms may communicate via a network. The network may includea wireless carrier network, a local area network (LAN), a wide areanetwork (WAN), and/or so forth.

The collection module 212 may store the received service feature data ofthe RSP platforms in a service feature data store 222. In variousembodiments, the service feature data store 222 may include one or moredatabases, such as relational databases, object databases,object-relational databases, and/or key-value databases that store data.The service feature data for each RSP platform may be stored as relateddata entries in the one or more databases. Thus, as the interface module210 receives updated service feature data from an RSP platform, thecollection module 212 may update one or more data entries in thedatabases with the most recent information. In some embodiments, thecollection module 212 may periodically activate the interface module 210to poll servers of the RSP platforms for service feature data. In otherembodiments, the servers of the RSP platform may periodically upload theservice feature data to the eSIM management platform 114 via theinterface module 210.

The analysis module 214 may rank RSP platforms that are specific todifferent geographical areas based on their service features. Forexample, the service features of an RSP platform may include ageographical area serviced by the RSP platform, an availability of theRSP platform to distribute eSIM profiles, a representative response timeof the RSP platform to requests for eSIM profiles, a reliability of theRSP platform in distributing eSIM profiles, available inventoryquantities of eSIM profiles for different user device types that arecarried by the RSP platform, and/or so forth.

The availability of the RSP platform may be measured via a ratio of anumber of times that the RSP platform responded to eSIM profile requestswithin a predetermined time limit to a number of times that the RSPplatform responded to eSIM profile requests outside of the predeterminedtime limit. The RSP platform is considered to have responded to an eSIMrequest when the RSP platform provides an eSIM profile to a user devicein response to the request. Such a ratio may be computed for apredetermined time period. The predetermined time period may be anactive lifetime of the RSP platform, a periodic time interval (firstquarter, second quarter, etc.), or a moving window of time (e.g., themost recent 60 days). The representative response time (e.g., 600milliseconds) of the RSP platform may be a mean, median, or mode of theresponse times of the RSP platform in a given time period. The giventime period may be an active lifetime of the RSP platform, a periodictime interval (first quarter, second quarter, etc.), or a moving windowof time (e.g., the most recent 60 days).

The reliability of the RSP platform may be measured by a percentage oftimes that the RSP platform responded to eSIM profile requests within amaximum timeout limit during a specific time period. The failure of theRSP platform to respond to the SIM profile request within the maximumtimeout limit is considered to be a failure to respond. The specifictime period may be an active lifetime of the RSP platform, a periodictime interval (first quarter, second quarter, etc.), or a moving windowof time (e.g., the most recent 60 days). In alternative embodiments, thereliability of the RSP platform may be measured by a number of timesthat the RSP platform responded to eSIM profile requests within amaximum timeout limit during a specific time period. An availabilityinventory quantity of eSIM profiles for a particular user device typemay refer to the number of the eSIM profiles stored by an RSP platformthat is available for distribution to user devices. For example, a userdevice type may be a classification of a user device based on a devicemodel, a device manufacturer, a device operating system, and/or soforth.

In some embodiments, the analysis module 214 may use minimal servicefeature requirements to determine whether an RSP platform is to beincluded or excluded from a preferred RSP platform list for a particulargeographical area. For example, the minimal service requirements mayinclude a minimum available requirement, a maximum response timerequirement, a minimum reliability requirement, a minimum availabilityinventory quantity requirement, etc. Such requirements may be in theform of ratios, numerical values, percentage values, and/or so forth.Accordingly, an RSP platform that services a geographical area may beincluded in a preferred RSP platform list for the geographical area wheneach service feature of the RSP platform meets a corresponding servicefeature requirement. Otherwise, the RSP platform may be excluded from apreferred RSP platform list.

Furthermore, the analysis module 214 may rank the multiple RSP platformsthat are eligible for inclusion in a preferred RSP platform list fromthe most preferred to the least preferred. In some instances, theanalysis module 214 may rank the multiple RSP platform based on one ormore service features that are deemed the most important. For example,if RSP platform reliability is the most important, then the multiple RSPplatforms may be ranked according to their respective reliabilitymeasurements. Further, if RSP platform response time is the next mostimportant, then any RSP platforms that have identical reliabilitymeasurements may be ranked based on their response times, and so on andso forth. Thus, a first RSP platform with the shorter response time willbe ranked as more preferred than a second RSP platform that has a longerresponse time. An additional distinction in preference can also be madebased on RSP platform availability, in which an RSP platform that ismore available is preferred over an RSP platform that is less available.In this way, the analysis module 214 may use the importance of servicefeatures to rank each of the multiple RSP platforms in an order ofpreference.

In other instances, the analysis module 214 may calculate a preferencevalue for each of the multiple RSP platforms that are eligible forinclusion in a preferred RSP platform list. The multiple RSP platformsare then positioned in the preferred RSP platform list according totheir preference values. The preference value for an RSP platform may becalculated by first assigning a weighting value to each of the servicefeature measurements of the RSP platform. In various embodiments, theweighting value assigned to each service feature measurement may be apositive value or a negative value. The product of each service featurevalue and weighting value pair of the RSP platform is then calculated bythe analysis module 214. The products for the service features of theRSP platform are then summed together to generate the preference valuefor the RSP platform. Subsequently, the analysis module 214 maydesignate the RSP platform of the multiple RSP platforms with thehighest preference value as the most preferred, as well as designate theremaining RSP platforms in order of preference according to theirsuccessive lower preference values. In instances where two or more RSPplatforms have identical preference values, other characteristics ofthese RSP platforms, such as a cost to the eSIM management platform 114,a geographical proximity to the eSIM management platform 114, etc. mayserve as tie breakers. For example, a lower cost or closer geographicalproximity may result in a higher preference ranking.

The distribution module 216 may distribute the preferred RSP platformfiles, such as the preferred RSP platform file 120, to user devices.Each of the preferred RSP platform files may contain one or morepreferred RSP platform lists. In the push-model, the distribution module216 may send a preferred RSP platform file to a user device on aperiodic basis or on the occurrence of certain events. For example, thedistribution module 216 may receive a notification from the wirelesscarrier network of the MNO 104 indicating that the user device 102 haspowered on and registered with the wireless carrier network of the MNO104 or a partner MNO of the MNO 104. Accordingly, the distributionmodule 216 may send a preferred RSP platform file to the user device102. In turn, the LPA application 112 on the user device 102 may receivethe preferred RSP platform file and store the file in the eSIM 110 or inanother memory location of the user device 102. In another example, thedistribution module 216 may receive a notification from the wirelesscarrier network of the MNO 104 indicating that the user device 102 isapproaching within a predefined distance of a boundary for ageographical area served by the wireless carrier network of the MNO 104.This may be determined by the user device 102 connecting to a particularbase station node of the wireless carrier network that is proximate tothe boundary. In response to such a detection, the distribution module216 may send a preferred RSP platform file to the user device 102.

In the pull-model, the LPA application 112 on the user device 102 may beconfigured to request an updated version of a preferred RSP platformfile from the distribution module 216 on a periodic basis or on theoccurrence of certain events. For example, these events may include theuser device 102 rebooting, and/or powering on and registering with thewireless carrier network of the MNO 104.

The user interface module 218 may enable an administrator to interactwith the eSIM management platform 114 via user interface controls. Theuser interface controls may include a data output device (e.g., visualdisplay, audio speakers), and one or more data input devices. The datainput devices may include, but are not limited to, combinations of oneor more of keypads, keyboards, mouse devices, touch screens,microphones, speech recognition packages, and any other suitable devicesor other electronic/software selection methods. Accordingly, theadministrator may use the user interface module 218 to perform taskssuch as viewing the service features of various RSP platforms, inputtingone or more service parameters, modifying the various service parameterrequirements, and/or so forth.

Example Computing Device Components

FIG. 3 is a block diagram showing various components of an illustrativeuser device that executes the LPA application to selectively downloadthe new eSIM profile. The user device 102 may include a communicationinterface 302, one or more sensors 304, a user interface 306, one ormore processors 308, memory 310, and device hardware 312. Thecommunication interface 302 may include wireless and/or wiredcommunication components that enable the electronic device to transmitor receive voice or data communication via the wireless carrier network,as well as other telecommunication and/or data communication networks.The sensors 304 may include a proximity sensor, a compass, anaccelerometer, biometric sensors, cameras, and/or a global positioningsystem (GPS) sensor, among other appropriate sensors. The proximitysensor may detect the movement of objects that are proximate to the userdevice 102. The compass, the accelerometer, and the GPS sensor maydetect orientation, movement, and geolocation of the user device 102.The cameras may capture images of the environment around the user device102.

The user interface 306 may enable a user to provide input and receiveoutput from the user device 102. The user interface 306 may include adata output device (e.g., visual display, audio speakers), and one ormore data input devices. The data input devices may include, but are notlimited to, combinations of one or more of keypads, keyboards, mousedevices, touch screens, microphones, speech recognition packages, andany other suitable devices or other electronic/software selectionmethods.

The memory 310 may be implemented using computer-readable media, such ascomputer storage media. Computer-readable media includes, at least, twotypes of computer-readable media, namely computer storage media andcommunications media. Computer storage media includes volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules, orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other non-transmission medium that can be used to storeinformation for access by a computing device. In contrast, communicationmedia may embody computer-readable instructions, data structures,program modules, or other data in a modulated data signal, such as acarrier wave, or other transmission mechanisms.

The device hardware 312 may include a cellular modem that enables theuser device 102 to perform telecommunication and data communication withone or more wireless carrier networks, as well as a short-rangetransceiver that enables the device to connect to other devices viashort-range wireless communication links. The device hardware 312 mayfurther include signal converters, antennas, hardware decoders andencoders, graphics processors, and/or the like that enable the userdevice 102 to execute applications and provide telecommunication anddata communication functions. The cellular modem may be driven by modemsoftware to perform telecommunication and data communication with awireless communication network. The modem software may be firmware thatis stored in dedicated non-volatile memory of the user device 102. Suchnon-volatile memory may include read-only memory (ROM), erasableprogrammable read-only memory (EPROM), or flash memory. The user deviceis further equipped with the eSIM 110 that stores one or more eSIMprofiles.

The one or more processors 308 and the memory 310 of the user device 102may implement an operating system 314, device software 316, one or moreapplications 318, and the LPA application 112. Such software may includeroutines, program instructions, objects, and/or data structures that areexecuted by the processors 308 to perform particular tasks or implementparticular abstract data types.

The operating system 314 may include components that enable the userdevice 102 to receive and transmit data via various interfaces (e.g.,user controls, communication interface 302, and/or memory input/outputdevices). The operating system 314 may also process data using the oneor more processors 308 to generate outputs based on inputs that arereceived via the user interface 306. For example, the operating system314 may provide an execution environment for the execution of theapplications 318. The operating system 314 may include a presentationcomponent that presents the output (e.g., display the data on anelectronic display, store the data in memory, transmit the data toanother electronic device, etc.).

The operating system 314 may include an interface layer that enablesapplications to interface with the modem and/or the communicationinterface 302. The interface layer may comprise public APIs, privateAPIs, or a combination of both public APIs and private APIs.Additionally, the operating system 314 may include other components thatperform various other functions generally associated with an operatingsystem. The device software 316 may include software components thatenable the user device to perform functions. For example, the devicesoftware 316 may include basic input/output system (BIOS), bootrom, or abootloader that boots up the user device 102 and executes the operatingsystem 314 following power-up of the device.

The applications 318 may include applications that provide utility,entertainment, and/or productivity functionalities to a user of the userdevice 102. For example, the applications 318 may include telephonyapplications, electronic mail applications, remote desktop applications,web browser applications, navigation applications, office productivityapplications, multimedia streaming applications, an online shoppingapplication, and/or so forth.

The LPA application 112 may include a platform update module 320 and adownload module 322. Such modules may include routines, programinstructions, objects, and/or data structures that are executed by theprocessors 204 to perform particular tasks or implement particularabstract data types. The LPA application 112 may communicate with one ormore computing devices of the Mill platform via a network. The networkmay include a wireless carrier network, a local area network (LAN), awide area network (WAN), and/or so forth.

The platform update module 320 may obtain preferred RSP platform files,such as the preferred RSP platform file 120, from an eSIM managementplatform of the MNO 104 via a pull-model or a push-model. In thepull-model, the platform update module 320 may periodically request anupdated version of the preferred RSP platform file 120 from the eSIMmanagement platform for storage in the eSIM 110. In the push-model, theeSIM management platform 114 may periodically send the most updatedversion of the preferred RSP platform file 120 to the platform updatemodule 320. In turn, the platform update module 320 may store the mostupdated version in the eSIM 110.

The download module 322 may be configured to send an eSIM profilerequest to an RSP platform that services a geographical area. In someembodiments, the download module 322 may select the RSP platform basedon a preferred RSP platform list for the geographical area. For example,the RSP platform may be the most preferred RSP platform listed in thepreferred RSP platform list. In some embodiments, the download module322 may make the selection when the user device 102 determines viageolocation data that the user device 102 has moved from a firstgeographical area served by the MNO 104 to a geographical area servicedby a partner MNO of the MNO 104. However, in other embodiments, thedownload module 322 may initiate the request when the user device 102initially powers up while located in a geographical area.

The eSIM profile request may include a device identifier of the userdevice 102, an identifier of the eSIM 110, a network identifier of theMNO 104, i.e., home wireless carrier network, geolocation information ofthe user device 102, a network identifier of the MNO for which the eSIMprofile is being sought, and/or other identification information. Inturn, the RSP platform may prepare and send an eSIM profile that isspecific for the partner MNO 106 to the user device 102. Further, theRSP platform may activate a billing function of the partner MNO 106,such as an Online Charging System (OCS) or another equivalent corenetwork component, to track the usage of telecommunication services bythe user device 102. The tracked usage information is used by thebilling function to bill a subscriber account established for the userdevice 102 or pass through the charges to a subscriber account that isassociated with the user device 102 and established with the MNO 104.

The download module 322 may store the eSIM profile into the eSIM 110.The eSIM profile is then used by the user device 102 to accesstelecommunication services from the partner MNO. In some instances, thestorage of the eSIM profile that is specific to partner MNO (e.g., eSIMprofile 128) into the eSIM 110 may include a replacement of an existingeSIM profile (e.g., eSIM profile 108 that is specific to the MNO 104) inthe eSIM 110. However, in other instances, the eSIM profile that isspecific to partner MNO may be stored in the eSIM 110 along with anexisting eSIM profile.

In some instances, the download module 322 may be unable to receive arequested eSIM profile that is specific to an MNO from an RSP platformwithin a predetermined period of time. This may occur due to an error oroutage that occurs at the RSP platform. In such instances, the downloadmodule 322 may automatically request another eSIM profile that isspecific to the MNO from the next most preferred RSP platform, and so onand so forth. Accordingly, the download module 322 may proceed down thepreferred RSP platform list in the event of one or more additional eSIMprofile download failures until the download module 322 is able toobtain the eSIM profile specific to the MNO from an RSP platform on thelist.

In some embodiments, the download module 322 may blacklist an RSPplatform that is unable to provide eSIM profiles for a predeterminednumber of times (e.g., three times). In such embodiments, the RSPplatform is deemed to be unable to provide an eSIM profile when the RSPplatform is unable to provide the eSIM profile within a pre-establishedtime limit (e.g., 700 milliseconds). In some instances, the downloadmodule 322 may perform the blacklisting by removing the RSP platformfrom the corresponding preferred RSP platform list. In other instances,the download module 322 may perform the blacklisting by placing the RSPplatform on an actual blacklist. In the latter instances, the downloadmodule 322 may verify that an RSP platform selected to provide an eSIMprofile is not on the blacklist before sending an eSIM profile requestto the RSP platform. However, if the RSP platform is on the blacklist,the download module 322 may skip the RSP platform and move to the nextmost preferred RSP platform.

Example Processes

FIGS. 4-6 present illustrative processes 400-600 for an LPA applicationon a user device to selectively download a new eSIM profile from aparticular RSP platform based on a preferred RSP platform list providedby an eSIM management platform. Each of the processes 400-600 isillustrated as a collection of blocks in a logical flow chart, whichrepresents a sequence of operations that can be implemented in hardware,software, or a combination thereof. In the context of software, theblocks represent computer-executable instructions that, when executed byone or more processors, perform the recited operations. Generally,computer-executable instructions may include routines, code segments,programs, objects, components, data structures, and the like thatperform particular functions or implement particular abstract datatypes. The order in which the operations are described is not intendedto be construed as a limitation, and any number of the described blockscan be combined in any order and/or in parallel to implement theprocess. For discussion purposes, the processes 400-600 are describedwith reference to the architecture 100 of FIG. 1.

FIG. 4 is a flow diagram of an example process 400 for an LPAapplication on a user device to obtain the new eSIM profile from apreferred RSP platform that is listed on an RSP platform list providedby the eSIM management platform. At block 402, the user device 102 mayreceive telecommunication services from an MNO using an MNO-specificeSIM stored on a user device while the user device is located in a firstgeographical area. In various embodiments, the MNO may be the MNO 104that operates a home wireless carrier network of the user device 102 ora partner MNO of the MNO 104.

At block 404, the LPA application 112 on the user device 102 may receivea list of preferred RSP platforms that distribute eSIM profiles specificto a partner MNO that provides telecommunication services for a secondgeographical area from an eSIM management platform 114 of the MNO 104.This partner MNO is different from the partner MNO described in block402. In various embodiments, the list may be organized in an order ofpreference, e.g., from a most preferred RSP platform to a leastpreferred RSP platform.

At block 406, the LPA application 112 may determine that the user devicehas moved to the second geographical area based on a geolocation of theuser device. In various embodiments, the LPA application 112 may makethis determination based on geolocation data detected by a GPS sensor ofthe user device 102.

At block 408, the LPA application 112 may download an eSIM profile forthe partner MNO of the MNO that serves the second geographical area froman RSP platform of one or more RSP platforms included in the list. Thedownload may include the LPA application 112 requesting the eSIM profilefrom a most preferred RSP platform in the list. In turn, the mostpreferred RSP platform may send the eSIM profile to the user device 102.The downloaded eSIM profile may be stored by the LPA application 112 inthe eSIM 110 of the user device 102. In some instances, the storage ofthe downloaded eSIM profile of the partner MNO may include replacing anexisting eSIM profile stored in the eSIM 110 with the eSIM profile ofthe partner MNO. However, in other instances, the downloaded eSIMprofile of the partner MNO may be stored along with the existing eSIMprofile in the eSIM 110.

In instances in which the most preferred RSP platform is unable toprovide the eSIM profile, the LPA application may automatically requestanother eSIM profile that is specific to the MNO from the next mostpreferred RSP platform, and so on and so forth. Accordingly, the LPAapplication 112 may proceed down the preferred RSP platform list in theevent of one or more additional eSIM profile download failures until theLPA application 112 is able to obtain the eSIM profile specific to theMNO from an RSP platform on the list.

At block 410, the user device 102 may access telecommunication servicein the second geographical area from the partner MNO of the MNO usingthe eSIM profile specific to the partner MNO. The user device 102 isable to access a wireless carrier network of the partner MNO using theeSIM profile specific to the partner MNO.

FIG. 5 is a flow diagram of an example process 500 for an eSIMmanagement platform to send a preferred RSP platform list of availableRSP platforms to an LPA application on a user device. At block 502, theeSIM management platform 114 may receive service feature information onmultiple RSP platforms that are designated by the MNO 104 to distributeeSIM profile for a partner MNO that provides telecommunication servicesin a geographical area. At block 504, the eSIM management platform 114may evaluate the multiple RSP platforms based on one or more servicefeatures of each RSP platform to select one or more RSP platforms of themultiple RSP platforms for population into a list of preferred RSPplatforms for the geographical area. The service features of an RSPplatform may include a geographical area serviced by the RSP platform,an availability of the RSP platform to distribute eSIM profiles, arepresentative (e.g., average) response time of the RSP platform torequests for eSIM profiles, a reliability of the RSP platform indistributing eSIM profiles, available inventory quantities of eSIMprofiles for different user device types that are carried by the RSPplatform, and/or so forth.

At block 506, the eSIM management platform 114 may populate the one ormore RSP platforms into the list of preferred RSP platforms for thegeographical area. At block 508, the eSIM management platform may sendthe list of RSP platforms to a user device to configure the user deviceobtain telecommunication services from the partner MNO while the userdevice is in the geographical area.

FIG. 6 is a flow diagram of an example process 600 for an eSIMmanagement platform to determine whether an RSP platform is to beincluded in a preferred RSP platform list. The example process 600 mayfurther describe block 504 of the example process 500. At block 602, theeSIM management platform 114 may determine whether an availability of anRSP platform that is capable of distributing eSIM profiles for a partnerMNO of the MNO 104 meets an availability requirement. At decision block604, if the RSP platform is determined to meet the availabilityrequirement, the process 600 may continue to block 606. At block 606,the eSIM management platform 114 may determine whether a representativeresponse time of the RSP platform meets a response time requirement. Atdecision block 608, if the RSP platform is determined to meet theresponse time requirement, the process 600 may continue to block 610.

At block 610, the eSIM management platform 114 may determine whether areliability of the RSP platform meets a reliability requirement. Atdecision block 612, if the RSP platform is determined to meet thereliability requirement, the process 600 may proceed to block 614. Atblock 614, the eSIM management platform 114 may determine whether atleast one inventory of the RSP platform meets one or more inventoryrequirements. At decision block 616, if the at least one inventory ofthe RSP platform meets one or more inventory requirements, the process600 may proceed to block 618. At block 618, the eSIM management platform114 may include the RSP platform in a list of preferred RSP platformsfor download to one or more user devices. In some instances, the RSPplatform may be placed in the list in preference order according to oneor more of its service feature measurements. In other instances, the RSPplatform may be placed in the list in preference order with respect toone or more other RSP platforms according to its preference value.

Returning to decision block 604, if the eSIM management platform 114determines that the availability of the RSP platform does not meet theavailability requirement, the process 600 may proceed to block 620. Atblock 620, the eSIM management platform 114 may exclude the RSP platformfrom the list of the preferred RSP platforms. Returning to decisionblock 608, if the eSIM management platform 114 determines that therepresentative response time of the RSP platform does not meet theresponse time requirement, the process 600 may also proceed to block620. Returning to decision block 612, if the eSIM management platform114 determines that the reliability of the RSP platform does not meetthe reliability requirement, the process 600 may also proceed to block620. Returning to decision block 616, if the eSIM management platform114 determines that at least one inventory of the RSP platform does notmeet one or more inventory requirements, the process 600 may alsoproceed to block 620.

The distribution of lists of available RSP platforms for differentgeographical areas to a user device enables the LPA application on theuser device to directly request an eSIM profile from an RSP platform asthe user device travels to a new geographical area. The use of an eSIMprofile for a partner MNO in the new geographical area may allow theuser device to avoid accruing out-of-network roaming fees for using thetelecommunication services provided by the partner MNO. In someinstances, the use of such an eSIM profile by the user device may alsoenable the user device to receive higher quality services and/oradditional service features from the partner MNO.

CONCLUSION

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as exemplary forms ofimplementing the claims.

What is claimed is:
 1. One or more non-transitory computer-readablemedia of a user device storing computer-executable instructions thatupon execution cause one or more processors to perform acts comprising:receiving telecommunication services using an embedded subscriberidentity module (eSIM) profile stored on the user device while the userdevice is located in a first geographical area; receiving a list ofpreferred remote SIM provisioning (RSP) platforms that provide eSIMprofiles specific to a partner MNO of the MNO in a second geographicalarea from an eSIM management platform of an MNO; determining the userdevice has moved to a second geographical area based on a geolocation ofthe user device; and downloading an additional eSIM profile specific tothe partner MNO of the MNO from an RSP platform of one or more RSPplatforms included in the list of preferred RSP platforms.
 2. The one ormore non-transitory computer-readable media of claim 1, wherein the actsfurther comprise receiving telecommunication services from the partnerMNO using the additional eSIM profile specific to the partner MNO in thesecond geographical area.
 3. The one or more non-transitorycomputer-readable media of claim 1, wherein the receivingtelecommunication services in the first geographical area includesreceiving the telecommunication services from the MNO or a partner MNOof the MNO via the eSIM profile.
 4. The one or more non-transitorycomputer-readable media of claim 1, wherein the RSP platform is a mostpreferred RSP platform in the list of preferred RSP platforms.
 5. Theone or more non-transitory computer-readable media of claim 1, whereinthe RSP platform is selected to provide the additional eSIM profile tothe user device following an indication that a more preferred RSPplatform on the list of is unable to provide the additional eSIM profileto the user device.
 6. The one or more non-transitory computer-readablemedia of claim 1, wherein the list of preferred RSP platforms ranksmultiple RSP platforms from a most preferred RSP platform to a leastpreferred RSP platform based on one or more service features of themultiple RSP platforms.
 7. The one or more non-transitorycomputer-readable media of claim 6, wherein at least one service featureof the RSP platform include a geographical area serviced by the RSPplatform, an availability of the RSP platform to distribute eSIMprofiles, a representative response time of the RSP platform to requestsfor the eSIM profiles, a reliability of the RSP platform in distributingthe eSIM profiles, at least one available inventory quantity of eSIMprofiles that are carried by the RSP platform for one or more userdevice types.
 8. A computer-implemented method, comprising: receiving,at a user device, telecommunication services using an embeddedsubscriber identity module (eSIM) profile stored on the user devicewhile the user device is located in a first geographical area;receiving, at the user device, a list of preferred remote SIMprovisioning (RSP) platforms that provide eSIM profiles specific to apartner MNO of the MNO in a second geographical area from an eSIMmanagement platform of an MNO; determining the user device has moved toa second geographical area based on a geolocation of the user device;and downloading, at the user device, an additional eSIM profile specificto the partner MNO of the MNO from an RSP platform of one or more RSPplatforms included in the list of preferred RSP platforms.
 9. Thecomputer-implemented method of claim 8, further comprising receivingtelecommunication services from the partner MNO using the additionaleSIM profile specific to the partner MNO in the second geographicalarea.
 10. The computer-implemented method of claim 8, wherein thereceiving telecommunication services in the first geographical areaincludes receiving the telecommunication services from the MNO or apartner MNO of the MNO via the eSIM profile.
 11. Thecomputer-implemented method of claim 8, wherein the RSP platform is amost preferred RSP platform in the list of preferred RSP platforms. 12.The computer-implemented method of claim 8, wherein the RSP platform isselected to provide the additional eSIM profile to the user devicefollowing an indication that a more preferred RSP platform on the listof is unable to provide the additional eSIM profile to the user device.13. The computer-implemented method of claim 8, wherein the list ofpreferred RSP platforms ranks multiple RSP platforms from a mostpreferred RSP platform to a least preferred RSP platform based on one ormore service features of the multiple RSP platforms.
 14. Thecomputer-implemented method of claim 13, wherein at least one servicefeature of the RSP platform include a geographical area serviced by theRSP platform, an availability of the RSP platform to distribute eSIMprofiles, a representative response time of the RSP platform to requestsfor the eSIM profiles, a reliability of the RSP platform in distributingthe eSIM profiles, at least one available inventory quantity of eSIMprofiles that are carried by the RSP platform for one or more userdevice types.
 15. A user device, comprising: one or more processors; andmemory including a plurality of computer-executable components that areexecutable by the one or more processors to perform a plurality ofactions, the plurality of actions comprising: receivingtelecommunication services using an embedded subscriber identity module(eSIM) profile stored on the user device while the user device islocated in a first geographical area; receiving a list of preferredremote SIM provisioning (RSP) platforms that provide eSIM profilesspecific to a partner MNO of the MNO in a second geographical area froman eSIM management platform of an MNO; determining the user device hasmoved to a second geographical area based on a geolocation of the userdevice; and downloading an additional eSIM profile specific to thepartner MNO of the MNO from an RSP platform of one or more RSP platformsincluded in the list of preferred RSP platforms.
 16. The user device ofclaim 15, wherein the plurality of actions further comprise receivingtelecommunication services from the partner MNO using the additionaleSIM profile specific to the partner MNO in the second geographicalarea.
 17. The user device of claim 15, wherein the receivingtelecommunication services in the first geographical area includesreceiving the telecommunication services from the MNO or a partner MNOof the MNO via the eSIM profile.
 18. The user device of claim 15,wherein the RSP platform is a most preferred RSP platform in the list ofpreferred RSP platforms.
 19. The user device of claim 15, wherein thelist of preferred RSP platforms ranks multiple RSP platforms from a mostpreferred RSP platform to a least preferred RSP platform based on one ormore service features of the multiple RSP platforms.
 20. The user deviceof claim 19, wherein at least one service feature of the RSP platforminclude a geographical area serviced by the RSP platform, anavailability of the RSP platform to distribute eSIM profiles, arepresentative response time of the RSP platform to requests for theeSIM profiles, a reliability of the RSP platform in distributing theeSIM profiles, at least one available inventory quantity of eSIMprofiles that are carried by the RSP platform for one or more userdevice types.